home *** CD-ROM | disk | FTP | other *** search
-
-
-
- - 1 -
-
-
-
- 2. _M_P_T__I_n_s_t_a_l_l_a_t_i_o_n__f_o_r__I_R_I_X__S_y_s_t_e_m_s
-
- This chapter provides information that you need to install
- MPT on IRIX systems. For details of MPT installation,
- contact your SGI support analyst.
-
-
- 2.1 _M_P_T__S_u_b_s_y_s_t_e_m_s
-
- The MPT for IRIX product includes the following subsystems:
-
-
- Subsystem Description
-
- mpi MPI 4.0 (MPT 1.6)
-
- sma SMA 3.2 (MPT 1.6)
-
-
- MPT release packages version 1.5.3 and prior also contained
- the PVM subsystem. As noted in chapter 1 of these relnotes,
- PVM has been unbundled and is now available as a stand-alone
- product via DCS (Download Cool Software).
-
- With MPT release packages between versions 1.4 and 1.5.2,
- the MPI, SMA, and PVM components enforced mutual
- prerequisites for each other so that sites could install
- only complete MPT packages. However, there is no functional
- dependency between PVM and either MPI or SMA.
-
- Installation of MPT 1.6 on a system that has an older MPT
- version installed will upgrade the SMA and MPI components.
- Installing MPT 1.6 will not remove previous versions of PVM.
- This is possible because logic was added to the MPT package
- such that the MPI and SMA components of the MPT 1.6 package
- would meet the prerequisites for any previous version of
- PVM.
-
- For example, the net effect of upgrading from MPT 1.4.0.2 to
- MPT 1.6 is that the resulting installation will allow MPI
- and SMA from the MPT 1.6 distribution to co-exist with PVM
- from the MPT 1.4.0.2 distribution.
-
- As stated earlier, PVM functionality does not depend on SMA
- and MPI; nor does MPI and SMA depend in any way upon PVM.
- The dependencies introduced for MPT 1.4 through 1.5.2 were
- only for packaging purposes.
-
- If you subsequently attempt to uninstall MPT 1.6, iiiinnnnsssstttt or
- sssswwwwmmmmggggrrrr will flag a conflict because of the packaging
- dependency of PVM on MPI and SMA.
-
-
-
-
-
-
-
-
-
-
-
- - 2 -
-
-
-
- If the intention is to reinstall a previous version of MPT,
- MPT 1.4.0.2 for example, you should simply remove PVM along
- with the MPT 1.6 uninstallation. You will regain PVM upon
- reinstallation of the previous version of MPT, MPT 1.4.0.2
- in this example.
-
-
-
- 2.2 _D_i_s_k__S_p_a_c_e__R_e_q_u_i_r_e_m_e_n_t_s
-
- Disk space requirements for the MPT for IRIX product are
- approximately 21.2 MB, with approximately 1.5 MB overhead
- during installation.
-
-
- 2.3 _P_r_e_r_e_q_u_i_s_i_t_e_s
-
- Prerequisites for the MPT for IRIX product are as follows:
-
- +o To install the mpi subsystem, you must also install the
- sma subsystem.
-
- +o The manuals must have the insight_base.sw.eoe subsystem
- installed.
-
- +o The eoe.sw.base (6.5+) must be installed.
-
- +o The MPI component requires Array Services version 3.1
- or higher.
-
- 2.4 _I_n_s_t_a_l_l_i_n_g__I_n__a_n__A_l_t_e_r_n_a_t_e__L_o_c_a_t_i_o_n
-
- MPT software can be installed in an alternate location for
- use with the Modules software package. Chapter 4 of the
- release notes for the Modules product describes how to
- install MPT for use with Modules. You can obtain these
- relnotes by using the following command:
-
- rrrreeeellllnnnnooootttteeeessss mmmmoooodddduuuulllleeeessss 4444
-
- If MPT software has been installed on your system for use
- with Modules, you can access the software with the mmmmoooodddduuuulllleeee
- command.
-
- If MPT has not been installed for use with Modules, the
- software resides in default locations on your system
- (////uuuussssrrrr////iiiinnnncccclllluuuuddddeeee, ////uuuussssrrrr////lllliiiibbbb, and so on), as in previous
- releases.
-
- If you are installing MPT in a nondefault location, you must
- update the MANPATH environment variable, as in the following
-
-
-
-
-
-
-
-
-
-
-
- - 3 -
-
-
-
- example (_M_P_I_R_O_O_T is the non-default location):
-
- sssseeeetttteeeennnnvvvv MMMMAAAANNNNPPPPAAAATTTTHHHH $_M_P_I_R_O_O_T////uuuussssrrrr////mmmmaaaannnn::::////uuuussssrrrr////mmmmaaaannnn::::////uuuussssrrrr////llllooooccccaaaallll////mmmmaaaannnn
-
- 2.5 _S_w_a_p__C_o_n_f_i_g_u_r_a_t_i_o_n__R_e_c_o_m_m_e_n_d_a_t_i_o_n_s
-
- To run applications that use the MPI or SHMEM components of
- this distribution optimally, it might be necessary for your
- system administrator to configure virtual and logical swap
- space.
-
- To enable certain optimization features, 64-bit MPI and
- SHMEM applications employ shared memory optimization
- techniques that require large reservations of swap space,
- although most of the space is not actually used. However,
- if sufficient swap space is unavailable, large MPI jobs can
- fail at job startup. To avoid this problem, virtual swap
- space should be configured on the system.
-
- MPI and SHMEM 64-bit applications make use of the
- MMMMAAAAPPPP____AAAAUUUUTTTTOOOORRRREEEESSSSEEEERRRRVVVV feature of mmmmmmmmaaaapppp. This feature permits the
- application to allocate large amounts of virtual memory
- without actually reserving space on swap until pages are
- faulted in. Long running, memory-intensive MPI applications
- using large numbers of processors may fault in a significant
- number of these pages, in addition to pages faulted in for
- the heap or stack of each process. This can lead to a
- significant increase in swap space requirements. If the
- operating system begins making significant use of the swap
- device(s), and sufficient logical swap is unavailable, the
- operating system will begin to kill processes.
-
- To avoid this problem, additional logical swap space must be
- configured. In cases in which MPI jobs are expected to
- consume most of the available memory on the system, logical
- swap space should be configured to be at least twice the
- size of physical memory on the system.
-
- The sssswwwwaaaapppp(1M) man page provides details for configuring
- logical and virtual swap space.
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-